Release 10.1A: OpenEdge Deployment:
Startup Command and Parameter Reference

Directory Size (-D)

Use Directory Size (-D) to change the number of compiled procedure directory entries.

Operating system and syntax	UNIX Windows	-D n
Use with	Maximum value	Minimum value	Single-user default	Multi-user default
Client Session	500	5	100	100

n

The number of compiled procedure directory entries.

Each compiled procedure executed during an OpenEdge session requires a directory entry. A compiled procedure can be a session-compiled version of a procedure or a precompiled r-code version.

When Progress creates a session-compiled version of a procedure and there is no available space in the directory, it discards the oldest inactive compilation of a procedure. The next time the discarded procedure is run, Progress must recompile it if it was a session compile, or reopen and reread it if it was a precompiled r-code version.

The -D limit is a soft limit. If your application needs to exceed the limit, Progress automatically increases the number of directory entries by 50 percent and dynamically allocates memory for the expanded array. (Use the Statistics (-y) parameter to check the current directory size (-D) value. If the amount of memory necessary for allocating the expanded array is exceeded or if the size of the expanded array exceeds 31K, Progress exits the session.) When the limit is reached, Progress issues a WARNING message, which is written to the current output (if there is current output) and to the log file (LG).

You can force Progress to adhere to the specified directory size (-D) limit by starting the session with the Hardlimit (-hardlimit) startup parameter. When you use the -hardlimit startup parameter, Progress issues a WARNING message when you exceed the directory size limit. It also issues a message that a resource limit was reached and raises an untrappable STOP condition. Note that -hardlimit also enforces the limits set by the Local Buffer Size (-l), the Maximum Memory (-mmax), and the Nested Blocks (-nb) startup parameters, so the STOP condition is raised when any of the specified limits are reached.